From enquiry to balance sheet, in one workflow.

A complete reference for the Mazillo platform used by Navtek Marine Services — every operation, the document flow that ties them together, reporting, role-based access, and the coordinator commission engine.

Mazillo is the operations platform for Navtek Marine Services. It runs the full commercial lifecycle of a marine service or supply job — from the first customer enquiry, through quotation, order execution and sub-vendor purchasing, to tax invoicing, payment tracking and a live profit-and-loss balance sheet.

Every record is connected: a quotation knows its enquiry, an order knows its quote, an invoice knows its order, and the balance sheet rolls those links into order-wise margins. The same chain feeds the reporting suite and the coordinator commission engine, so a single data entry never has to be repeated downstream.

Data is stored locally per browser and moves between machines through a JSON backup & restore. The production database build follows once this workflow is signed off.

The left navigation exposes ten modules. Visibility is governed by the signed-in user's role (see §08). The first five are the operational spine; the rest are analytics, monitoring and administration.

A single thread runs from enquiry to balance sheet. Each stage hands its data to the next; two derived processes — service reporting and commission — branch off the order; and every stage feeds the reporting layer.

A branch off the order, the service report is the engineer's field record of work carried out on a vessel. It documents the equipment, the fault, the work done, time on the job and customer satisfaction — and links back to its order.

The Reports module slices the same connected data nine ways, each with date filtering and Excel export. It is the analytic mirror of the operational flow. Visibility follows permissions: View all reports shows every record, while View own reports limits a user to the cases and orders they coordinate — together with the invoices, sub-vendor POs and service reports linked to those orders, and nothing else.

Each report supports a date range and exports to Excel (.xls). The Case Master, Orders and Balance Sheet each have a dedicated export.

The balance sheet is the financial endpoint of the flow. For each order it computes profitability directly from the linked invoices and recorded costs.

Users are created in Settings with a name, email, password and a set of permissions. An admin assigns one or more permissions per user — there are no fixed roles — and the navigation shows only the modules a user's permissions allow. Users can be disabled (kept for history) rather than deleted. The assignable permissions are: Create enquiries, Create quotations, Create orders, Create invoices, Service engineer (own assigned reports only), View own reports, View all reports, View balance sheet, and Admin (all operations). A service engineer sees and edits only the service reports assigned to them.

The presets below are convenient starting points an admin can mix and match per user.

Coordinators are rewarded for converting enquiries into orders. One rule, set in Settings, applies to every non-cancelled order and rolls up per coordinator on the Coordinators page. Each enquiry that becomes an order counts as one conversion.

The Coordinators page surfaces the rollup: Total Commission Payable, Orders Converted and Active Coordinators, a per-coordinator performance table (orders handled, on hold, basis, commission) and an order-by-order commission detail. Coordinators see only their own figures; managers and admins see everyone.